Methods and apparatus for bifurcating data storage for enabling implementation and manipulation of an interactive hierarchical entitlement structure

ABSTRACT

A method for bifurcating data storage to enable implementation and manipulation of an interactive entitlement structure is provided. The method may include displaying a GUI and copying information corresponding to the list of entitlements to using one or more features associated with the GUI. The method may copy from a remote System of Record to a cache memory local to the GUI. The method may include displaying on the GUI signatories with an entitlement authorization; receiving a modification of the entitlement authorization; and extracting a signature of a signatory with entitlement authorization. An input signal may be received that indicates an input signal indicator is hovering over the signatory and displaying, on the GUI, in response to the hovering indication, 1) a copy of the signature of the signatory; 2) a hierarchal list of signatories with current entitlement authorization; and/or 3) a listing of documents signed by a signatory.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part application ofnon-provisional U.S. patent application Ser. No. 14/615,493, entitled,“METHOD AND APPARATUS FOR PROVIDING AN INTERACTIVE HIERARCHICALENTITLEMENT MAP”, filed on Feb. 6, 2015.

FIELD OF TECHNOLOGY

This application relates to providing robust systems for display of,inter alia, interactive hierarchical entitlement features andenforcement of same.

BACKGROUND OF THE DISCLOSURE

Hierarchical maps may be used to show entity hierarchies. Hierarchicalmaps may be one of a number of various features that are used in certainapplications. Such features may include responding to client requests,opening new accounts with pre-determined characteristics, reviewing andsubmitting such opened accounts for approval, maintaining such accountsor other accounts where such maintenance relates to addressidentification or statement maintenance or authorized signer maintenanceon such accounts, adding services for such accounts, enabling users toselect landing sites for clients and enabling users to add or modifyservices related to such accounts.

It would be desirable to combine many of the features set forth aboveinto a preferably single, interactive and robust application.

It would also be desirable to support interactivity between thefeatures.

SUMMARY OF THE INVENTION

Enforcing entitlements relates to restricting information access only toauthorized parties. Enforcing entitlements is critical to every page ofcertain applications. In addition, a database system of record whichhouses close to 150 columns of data may include 5-10 columns associatedwith enforcing entitlements. Such a database system may be relevant to aselected profile. In order to allow access to various locations, such adatabase system is typically stored at a distance from the applicationin use. Such a database may typically be stored in remote locations atleast because of the size of the system of record. The inventionproposes copying the 5-10 columns associated with enforcing entitlementsfrom the System of Record and storing the information in local storage,and, in certain embodiments, even in local cache memory, in order toenable enforcement of entitlements across all application locationswithout requiring the application to continuously communicate with theremote system of record to retrieve entitlement enforcement information.

A method for displaying hierarchal client entitlement information in agraphical user interface (“GUI”) is provided. The method may includequerying a list of entitlements for a client. The list may include alist of signatories with entitlement authorization. The method mayfurther include displaying, on the GUI, the list of entitlements for theclient. The displaying may include arranging the GUI with at least threerows of entitlement authorization levels. Each of the rows ofentitlement authorization may preferably corresponding to a differentlevel of entitlement authorization. The method may further includereceiving, from the client, entitlement authorization for a signatory.The method may also include adding the signatory to the list, linkingthe signatory to one or more signature documents associated with thesignatory's authorization and receiving a modification of the clientinformation. The method may also include transmitting, only if themodification is input by the signatory, the modification independent ofany human input to a System of Record. Thereafter, the method mayinclude transforming, when received by the System of Record, themodified client information into updated client information reflectingthe modification.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the invention will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 shows an illustrative apparatus in accordance with principles ofthe invention;

FIG. 2 shows an illustrative apparatus in accordance with the principlesof the invention;

FIG. 3 shows an illustrative flow diagram according to certainembodiments;

FIG. 4 shows another illustrative flow diagram in accordance with theprinciples of the invention;

FIG. 5 shows yet another illustrative flow diagram in accordance withthe principles of the invention;

FIG. 6 shows a hierarchical map in accordance with principles of theinvention;

FIG. 7 shows a user profile according to certain embodiments;

FIG. 8 shows a first listing of account details according to certainembodiments;

FIG. 9 shows an informational screen that is responsive to a selectionof a “My requests” tab according to certain embodiments;

FIG. 10 shows an informational screen that is responsive to a selectionof a “company requests” tab according to certain embodiments;

FIG. 11 shows a copy utility for opening an account according to certainembodiments;

FIG. 12 shows an array of information reporting options according tocertain embodiments;

FIG. 13 shows an account review and submit screen according to certainembodiments;

FIG. 14 shows an account maintenance screen according to certainembodiments;

FIG. 15 shows the account maintenance screen shown in FIG. 14 where theuser has selected signer maintenance according to certain embodiments;

FIG. 16 shows a screen for adding or updating services according tocertain embodiments;

FIG. 17 shows a transaction research screen according to certainembodiments;

FIG. 18 shows an approval screen according to certain embodiments;

FIG. 19 shows an alerts and landing page setting screen according tocertain embodiments;

FIG. 20 shows the hierarchical map of FIG. 6 as coupled to a remotesystem of record database according to certain embodiments;

FIG. 21 shows the hierarchical map of FIG. 6 as coupled to a remotesystem of record database according to certain embodiment, wherein aportion information related to entitlement enforcement is stored locallyaccording to certain embodiments;

FIG. 22 shows a conventional illustrative flow diagram; and

FIG. 23 shows illustrative flow diagram according to certainembodiments.

DETAILED DESCRIPTION OF THE DISCLOSURE

Apparatus, methods and media (collectively referred to herein as a“system”) for providing a hierarchal client entitlement map areprovided.

For the sake of illustration, the invention will be described as beingperformed by a “system.” The “system” may include one or more of thefeatures of the apparatus and methods that are shown or described hereinand/or any other suitable device or approach. The “system” may beprovided by an entity. The entity may be an individual, an organizationor any other suitable entity.

The system may query a list. The list may include a list ofentitlements. The entitlements may include entitlements for a client.The list may be a list for a client.

The system may display the list. The list may be displayed for theclient. The list may include a list of signatories. The signatories mayinclude signatories with authorization. The authorization may includeentitlement authorization.

The system may receive authorization. The authorization may be receivedfrom the client. The authorization may be entitlement authorization fora signatory. The system may add the signatory to the list.

The system may link the signatory. The signatory may be linked to one ormore documents. The documents may be signature documents. The signaturedocuments may be associated with the signatory's authorization.

The system may receive a modification. The modification may be amodification to information. The information may be client information.

The system may transmit the modification. The modification may betransmitted if the modification is input by the signatory. Themodification may be transmitted only if the modification is input by thesignatory. The modification may be input independent of any input. Themodification may be transmitted to a System of Record. The modificationmay be transmitted to the System of Record without any human input.

The system may transform the modified client information. The system maytransform the information upon receipt by the System of Record. Theinformation may be transformed into updated client information. Theupdated information may reflect the modification.

The signatory may be a first signatory. The first signatory may beprovided with an entitlement level. The entitlement level may be a firstentitlement level. The first entitlement level may correspond to thefirst signatory.

The signatory may be a second signatory. The second signatory may beprovided with an entitlement level. The entitlement level may be asecond entitlement level. The second entitlement level may correspond tothe second signatory.

The first signatory may be identified on the list of signatories. Thesecond signatory may be identified on the list of signatories. The firstsignatory and/or the second signatory may be identified on the list ofsignatories as authorized to modify documents. The documents may beclient documents.

The signatories may be identified on the list of signatories asauthorized to submit changes. The changes may include changes todocuments. The documents may include client documents.

The modification to the documents may be transmitted using any known andavailable methods. The modification to the documents may be transmittedusing Straight Through Processing. The modification may be transmittedwithout human intervention.

The client information may be transmitted in any suitable form. Theclient information may be transmitted in batch form. The clientinformation may be transmitted in paragraph form.

The system may be configured for providing signatory maintenance.

The system may display a list. The list may be a hierarchal list. Thehierarchal list may be a list of signatories. The list of signatoriesmay include at least one authorization. The authorization may be anentitlement authorization.

The system may receive a modification. The modification may be receivedfrom the client. The modification may include a modification at leastone entitlement authorization.

The system may extract a signature. The signature may be extracted fromone or more documents. The documents may be client documents. Thesignature may be a signature of a signatory. The signatory may beassociated with entitlement authorization. The signatory may havepreviously been granted entitlement authorization.

The system may include a Graphical User Interface (“GUI”). The systemmay include a display. The system may display signatory information uponthe GUI.

The system may hover over signatory information on the GUI. The systemmay hover over the signatory on the GUI.

The system may display information on the display. The display may be ahierarchal display. The information may be displayed on the hierarchaldisplay in response to the hovering.

The system may display a copy of the signature of the signatory. Thecopy of the signature of the signatory may be displayed in response tothe system hovering over the signatory on the GUI.

The system may display a list. The list may be a list of signatories.The list of signatories may be a hierarchal list of signatories. Thelist of signatories may include signatories with authorization. Theauthorization may be entitlement authorization. The entitlementauthorization may be current entitlement authorization. The hierarchallist of signatories may be displayed in response to the system hoveringover the signatory on the GUI.

The system may display a listing of documents. The listing of documentsmay be a list of documents signed by a signatory. The listing ofdocuments may be a list of all documents signed by a signatory. Thelisting of documents may include a list of documents signed by each ofthe signatories. The listing of documents may be displayed in responseto the system hovering over the signatory on the GUI.

The system may receive a change. The change may be a change ofentitlement. The entitlement may be entitlement for a signatory. Inresponse to a change of entitlement for a signatory, the system mayremove the signatory. The signatory may be removed as an authorizedsignor. The signatory may be removed from an authorized signor database.

The system may include a selectable display. The listing of documentsmay include the selectable display. The selectable display may include adisplay of documents signed by the signatory.

An exemplary embodiment is now provided. The system may provide ahierarchal entitlement map. The system may query a list. The list mayinclude a list of entitlements. The list may be a list for a client. Theentitlements may include client entitlements.

The system may include a display. The display may be configured todisplay the list. The list may be displayed for the client. The list mayinclude a list of signatories. The signatories may be grantedauthorization. The authorization may include entitlement authorization.

The system may receive entitlement authorization. The authorization maybe an authorization of entitlement for a signatory. The authorizationmay be received from the client.

The system may receive a request. The request may include a request toadd the signatory. The request may include a request to add thesignatory to the list.

The system may receive a modification. The modification may include amodification to the client information.

The system may transmit the modification. The modification may only betransmitted if the modification is input by the signatory. Themodification may be transmitted independent of human input. Themodification may be transmitted to a System of Record.

The system may link the signatory. The signatory may be linked to one ormore signature documents. The one or more signature documents may beassociated with the signatory's authorization.

The system may transform the modified client information. The modifiedclient information may be transformed only when received by the Systemof Record. The modified client information may be transformed intoupdated client information. The updated client information may reflectthe modification.

The signatory may be a first signatory. The signatory may be a secondsignatory. The signatories may be identified on the list of signatories.The signatories on the list of signatories may be authorized to modifyclient documents.

The signatories on the list of signatories may be authorized to submitchanges to client documents.

The modification to client information may be transmitted using StraightThrough Processing. The modification to client information may betransmitted without human intervention.

Illustrative embodiments of apparatus and methods in accordance with theprinciples of the invention will now be described with reference to theaccompanying drawings, which form a part hereof. It is to be understoodthat other embodiments may be utilized and structural, functional andprocedural modifications may be made without departing from the scopeand spirit of the present invention.

FIG. 1 is an illustrative block diagram of system 100 based on acomputer 101. The computer 101 may have a processor 103 for controllingthe operation of the device and its associated components, and mayinclude RAM 105, ROM 107, input/output module 109, and a memory 115. Theprocessor 103 will also execute all software running on thecomputer—e.g., the operating system. Other components commonly used forcomputers such as EEPROM or Flash memory or any other suitablecomponents may also be part of the computer 101.

The memory 115 may be comprised of any suitable permanent storagetechnology—e.g., a hard drive. The memory 115 stores software includingthe operating system 117 any application(s) 119 along with any data 111needed for the operation of the system 100. Alternatively, some or allof computer executable instructions may be embodied in hardware orfirmware (not shown). The computer 101 executes the instructionsembodied by the software to perform various functions.

Input/output (“I/O”) module may include connectivity to a microphone,keyboard, touch screen, and/or stylus through which a user of computer101 may provide input, and may also include one or more speakers forproviding audio output and a video display device for providing textual,audiovisual and/or graphical output.

System 100 may be connected to other systems via a LAN interface 113.

System 100 may operate in a networked environment supporting connectionsto one or more remote computers, such as terminals 141 and 151.Terminals 141 and 151 may be personal computers or servers that includemany or all of the elements described above relative to system 100. Thenetwork connections depicted in FIG. 1 include a local area network(LAN) 125 and a wide area network (WAN) 129, but may also include othernetworks. When used in a LAN networking environment, computer 101 isconnected to LAN 125 through a LAN interface or adapter 113. When usedin a WAN networking environment, computer 101 may include a modem 127 orother means for establishing communications over WAN 129, such asInternet 131.

It will be appreciated that the network connections shown areillustrative and other means of establishing a communications linkbetween the computers may be used. The existence of any of variouswell-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like ispresumed, and the system can be operated in a client-serverconfiguration to permit a user to retrieve web pages from a web-basedserver. Any of various conventional web browsers can be used to displayand manipulate data on web pages.

Additionally, application program(s) 119, which may be used by computer101, may include computer executable instructions for invoking userfunctionality related to communication, such as email, Short MessageService (SMS), and voice input and speech recognition applications.

Computer 101 and/or terminals 141 or 151 may also be devices includingvarious other components, such as a battery, speaker, and antennas (notshown).

Terminal 151 and/or terminal 141 may be portable devices such as alaptop, cell phone, Blackberry™, or any other suitable device forstoring, transmitting and/or transporting relevant information.Terminals 151 and/or terminal 141 may be other devices. These devicesmay be identical to system 100 or different. The differences may berelated to hardware components and/or software components.

FIG. 2 shows illustrative apparatus 200. Apparatus 200 may be acomputing machine. Apparatus 200 may include one or more features of theapparatus shown in FIG. 1. Apparatus 200 may include chip module 202,which may include one or more integrated circuits, and which may includelogic configured to perform any other suitable logical operations.

Apparatus 200 may include one or more of the following components: I/Ocircuitry 204, which may include a transmitter device and a receiverdevice and may interface with fiber optic cable, coaxial cable,telephone lines, wireless devices, PHY layer hardware, a keypad/displaycontrol device or any other suitable encoded media or devices;peripheral devices 206, which may include counter timers, real-timetimers, power-on reset generators or any other suitable peripheraldevices; logical processing device 208, which may compute datastructural information, structural parameters of the data and/ordetermine signatory entitlement requirements and machine-readable memory210.

Machine-readable memory 210 may be configured to store inmachine-readable data structures: information pertaining to a signatory,information pertaining to an administrator of the repository and thesignatories which he may oversee, the current time, informationpertaining to historical entitlements, information relating to currentregulations, rules and/or statutes relating to account compliance and/orany other suitable information or data structures.

Components 202, 204, 206, 208 and 210 may be coupled together by asystem bus or other interconnections 212 and may be present on one ormore circuit boards such as 220. In some embodiments, the components maybe integrated into a single chip. The chip may be silicon-based.

FIG. 3 shows illustrative process 301 for providing a hierarchal cliententitlement map.

Process 301 for providing a hierarchal client entitlement map mayinitiate at step 303. At step 303, the system may query a list. The listmay include a list of entitlements. The entitlements may be entitlementsfor a client. The list may be queried for a client.

At step 305, the system may display the list of entitlements. The listof entitlements may be displayed for the client. The list may include alist of signatories. The signatories may be signatories withauthorization. The authorization may include entitlement authorization.

At step 307, the system may receive entitlement authorization. Theentitlement authorization may be received from the client. Theentitlement authorization may be authorization for a signatory.

At step 309, the system may add a signatory to a list of signatories.The signatory may be added to the list.

At step 311, the system may link the added signatory. The addedsignatory may be linked to one or more signature documents. The one ormore signature documents may be associated with the signatory'sauthorization.

At step 313, the system may receive a modification. The modification mayinclude a modification of client information.

At step 315, the system may transmit the modification. The modificationmay be transmitted preferably only if the modification is input by thesignatory. The modification may be transmitted independent of anyadditional human input. The modification may be transmitted to a Systemof Record.

At step 317, the system may transform the client information. The systemmay transform the client information into modified client information.The system may transform the information when received by the System ofRecord. The system may transform the information into updated clientinformation. The updated client information may reflect themodification.

FIG. 4 shows illustrative process for receiving entitlementauthorization from a client.

The process may begin at step 401. At step 401, the system may receiveauthorization. Authorization may be received from the client. Theauthorization may be entitlement authorization.

At step 403, the system may receive entitlement authorization. Theentitlement authorization may be received for a signatory. The signatorymay be a first signatory. The entitlement authorization may be receivedfrom the client.

At step 405, the system may provide an entitlement level. Theentitlement level may be a first entitlement level. The entitlementlevel may be associated with the first signatory. The first entitlementlevel may be the entitlement level of the first signatory.

At step 407, the system may add the first signatory to the client list.

At step 409, the system may receive entitlement authorization. Theauthorization may correspond to a second signatory. The authorizationfor the second signatory may be received from the client.

At step 411, the system may provide a second entitlement level. Thesecond entitlement level may be associated with the second signatory.The second entitlement level may be the entitlement level of the secondsignatory.

At step 413, the system may add the second signatory the client list.

Following receipt of a login by either the first signatory or the secondsignatory, step 415 shows transmitting entitlement enforcementinformation for storage local to the first signatory or the secondsignatory. Step 417 shows following a termination of a session by thelogged-on first signatory or the second signatory deleting thelocally-shared entitlement information.

FIG. 5 shows illustrative process 501 for providing signatorymaintenance.

Process 501 may begin at step 503. At step 503, the system may display alist. The list may be a hierarchal list. The list may be a list ofsignatories. The signatories may be associated with at least oneauthorization. The authorization may include entitlement authorization.

At step 505, the system may provide an entitlement level. Theentitlement level may be a first entitlement level. The entitlementlevel may be an entitlement level for a first signatory.

At step 507, the system may extract, preferably from local storage (butpossibly also from remote storage), a signature. The signature may bethe signature of a signatory. The signatory may have entitlementauthorization. The signatory signature may be extracted from one or moredocuments. The documents may be client documents.

At step 509, the system may include a GUI. The GUI May displayinformation. The GUI may display a pointer. The pointer may hover. Thepointer may hover over the signatory information. The pointer may bedisplayed on the hierarchal map. The pointer may be displayed hoveringover the signatory within the hierarchal map.

At step 511, the system may display information on a hierarchal mapdisplay. The information may be displayed in response to the hovering.

At step 513, the system may display a signature. The signature may be acopy of a signature. The signatory may be the signature of a signatory.The signatory may be the stored signature of a signatory. The signaturemay be retrieved from local storage.

At step 515, the system may display a list. The list may be a hierarchallist. The hierarchal list may be a list of signatories. The list mayinclude a list of signatories with entitlement authorization. Theentitlement authorization may be current entitlement authorization. Thehierarchal list may be retrieved from local storage.

At step 517, the system may display a listing of documents. The listingmay include documents signed by each of the signatories. The listing ofdocuments may be retrieved from local storage.

It should be noted that the information that is displayed in response tothe hovering, such as the information in any one of steps 513, 515and/or 517 may be shown in the alternative—i.e., only the information inone of 513, 515 or 517—or some combination of the information in two ormore of 513, 515 or 517 may be shown, without departing from the scopeof the invention.

FIG. 6 shows an embodiment of an illustrative hierarchal map 600. Map600 shows an illustrative company hierarchy tab 606.

Map 600 has been divided into three exemplary sections—i.e., executivemanagement, middle management and employees.

President 418 has preferably extended signatory authority for the entityto manager A (“M.A”) via document 616. Manager B (“M.B”) receivedsignatory authority via document 615 from ex-president 617 who is nolonger with the company.

M.A 614 has also extended signatory authority to Employee A (“E.A.”) 610via document 612.

In certain embodiments of the invention, when E.A 610 is removed fromsignatory authority, the hierarchical map 600 may preferably provide avisual indicator, or plurality of indicators, that E.A 610 derives hisauthority from M.A 614 and President 618.

Such a chain of authority, as well as the documents upon which the chainis based, may require reexamination in light of selected types ofoccurrences which caused M.A 610 to lose his signatory authority. Forexample, if M.A 610 lost his signatory authority because of a fraudulentact, then the chain of authority from which M.A 610 derived hissignatory authority may require inspection to insure that M.A 610'sfraud was not part of a greater, and more developed fraudulent scheme.

FIGS. 7-19 show a series of user interfaces that may, in certainembodiments, incorporate the disclosure set forth with respect to FIGS.1-6. Specifically, FIGS. 7-19 may, in certain embodiments, refer to,relate to or otherwise adapt the information shown in FIGS. 1-6, anddescribed in the portion of the specification corresponding thereto.

FIGS. 7-19 show a series of user interfaces that may, in certainembodiments, incorporate the disclosure set forth with respect to FIGS.1-6. Specifically, FIGS. 7-19 may, in certain embodiments, refer to,relate to or otherwise adapt the information shown in FIGS. 1-6, anddescribed in the portion of the specification corresponding thereto.

FIG. 7 shows a user profile 702. User profile 702 presents aconsolidated view of accounts 704, services 706 and authorized signatoryinformation 708 (alternatively referred to herein as “signers” or“signatories”).

FIG. 7 also enables export of information retrieved in response to acommand entered into profile 702, or in response to informationretrieved by a command entered into profile 702. Such export 710 may beformatted to export such information as an Excel file (manufactured byMicrosoft Corp. of Redmond, Wash.) or in some other suitable file.

FIG. 8 shows a first listing of account details 802 responsive to aselection of accounts 704 shown in FIG. 7.

FIG. 8 also shows account details 804 signatory information 806.Signatory information 804 preferably embodies methods and apparatus fordata warehousing with respect to the interactive hierarchicalentitlement map 600 shown in FIG. 6. It should be understood that, whilemap 600 shows an interactive hierarchical entitlement map 600, datashown in 806 supports such a map.

The signatory information data shown in 806 may preferably provide aninteractive pathway to available data relating to an interactivehierarchical entitlement map 600 shown in FIG. 6. For example, a usercould preferably leverage signatory information data 806 to as a conduitfor changing the data at a system of record level. Accordingly, anentitled user may be able to click on an authorized user shown in 806and be presented a system of record, interactive, screen for augmenting,adjusting, rejecting or otherwise changing the entitlement level of theselected, previously-entitled authorized user. It should be noted that,because the signatory information data in 806 is interactive, the datapathway between the screen shown in 806 and a system of record of such ascreen may preferably be, for the appropriately entitled viewers,bi-directional.

Alternatively, signatory information 806 may be viewed, but not changed,by a user with a different level of entitlement than the first user. Assuch, signatory information 806 may not be interactive to such a user.

FIG. 9 shows a “My Requests” tab 902. My requests tab 902 preferablyprovides details and status of a user's requests submitted through aservice center. The screen supporting my request tab 902 may preferablybe provided pursuant to a selection by a user of services 706 shown inFIG. 7.

It should be noted that requests can be filtered in order to manage therequests more easily. For example, a search for a request may beconducted using search box 904. In some embodiments, a search for arequest may be filtered by selecting one of request types 906.

Certain embodiments may identify a communications channel 908 associatedwith the request. For example, when a user requests, via an onlineportal, information regarding a missing check, the user request may beindicated as an online request, as shown in FIG. 9. In addition, myrequests may also present a status 910 identifier which provides avisual indication of the status of a user request.

FIG. 10 shows a company requests tab 1002. Company requests tab 1002 mayenable a user to view all requests regardless of channel. Such a tab ispreferably entitlement driven—i.e., a company's requests may preferablybe viewable only to the extent the user is entitled to view suchrequests. Again the channel associated with the request may be visibleat entry 1004.

FIG. 11 shows a copy utility 1102 within the create requests tab foropening an account. Copy utility 1102 may preferably enable a user toopen an account by selecting a legacy account from among a list oflegacy accounts, as shown at 1104, and requesting that the new accountbe opened according to the specifications of the selected legacyaccount.

FIG. 12 shows an array of information reporting options 1202. Such anarray 1202 may preferably enable a user to make any changes necessaryfor account services.

FIG. 13 shows an account review and submit screen. Such a screen maypreferably enable a user to browse for and retrieve necessarydocumentation 1302 for opening the account. A request may be submittedat 1304. FIG. 13 also enables a user, at 1306, to optionally route theaccount opening request for manual review and approval.

FIG. 14 shows an account maintenance screen. At 1402, the user ispreferably enabled to select either address maintenance and statementmaintenance or signer maintenance. At step 1404, the user is enabled tointeractively change an account address.

FIG. 15 shows the account maintenance screen shown in FIG. 14. Step 1502shows that the user has selected signer maintenance. At 1504, signermaintenance shows a selectable link to the document associated with thesigner designated in the account opening request.

FIG. 16 shows a screen for adding or updating services. The screenpreferably includes a list of selectable treasury services at 1602. Thescreen also preferably includes a list of online services at 1604. Uponselection of one of the list of services at 1602, or 1604, aninteractive dialogue box related to the requested service may appear, asshown at 1606.

FIG. 17 shows a transaction research screen. The transaction researchscreen preferably enables a user to request information regarding amissing transaction, as shown at 1702, or submit a general inquiry, asshown at 1704.

FIG. 18 shows an approval screen. The approval screen in FIG. 18preferably enables users to approve a selected account opening request,or reject a selected account opening request, as shown at 1802. Itshould be noted that the account screen in FIG. 18 may preferably onlybe available to users with the appropriate entitlement—i.e., anentitlement to approve or reject the requested account opening.

FIG. 19 shows an alerts and landing page setting screen. It should benoted that the alerts and landings screen may be available in responseto the selection of preferences selector 1902. Alerts request section1904 enables a user to select one or more alerts regarding varioustopics. A default landing page may be selected at 1906.

The default landing page may preferably be selectable from a mobiledevice only to the extent that the default landing page doesn'timplicate an immediate Oracle database interaction. To the extent that alanding page implicates an immediate Oracle database interaction, thatselection is preferably disallowed. At least one reason for this is thatthe mobile platform is not sufficiently robust, because of relativelysmaller bandwidth capabilities and the condensed screen associated withtypical mobile devices, to handle an immediate Oracle databaseinteraction. Specifically, a mobile platform may not support sufficientbandwidth to initiate contact at a screen including an immediate Oracledatabase interaction. As such, any screen that implicates an immediateOracle database interaction may preferably be excluded from selectionsat 1906.

FIG. 20 shows the interactive hierarchical entitlement map 2002 detailedat FIG. 6. FIG. 20 also shows that map 2002 may be coupled, byconnection 2006, to a remote system of record (“SOR”) database (“DB”)2004. DB 2004 may preferably include, inter alia, an entitlementenforcement portion of the DB.

It should be noted that the entitlement enforcement portion of DB 2004typically comprises less than ten percent of the information stored inthe DB. For example, if the entire DB comprised 150 columns ofinformation, the entitlement enforcement portion of the DB may includebetween five and ten columns.

In certain conventional systems, the remote connection to the DB 2004drained resources and increased latency because of the repeated calls tothe DB whenever entitlement information was needed. Further, it shouldbe noted that all the screens shown in FIGS. 7-19 required some level ofentitlement information. As such, when DB 2004 is remote, the systemsand methods shown in FIGS. 7-19, and described in the portion of thespecification corresponding thereto, required near-continuousinteraction with remote DB 2004.

FIG. 21 shows a bifurcation of DB 2004 into two component parts—i.e.,SOR DB less entitlement enforcement portion of DB 2104 and local memoryor cache entitlement portion of SOR DB at 2108. It should be noted thatcache entitlement portion of SOR DB at 2108 enables a user to implementthe systems and methods shown in FIGS. 7-19 absent a remote interaction.As such all the entitlement-based interactions occur locally and thespeed with which the systems and methods may be implemented is greatlyimproved. Thus, the bifurcation of DB 2004, shown in FIG. 20, into DB2104 and 2108 shown in FIG. 21 may be understood to be an architecturethat greatly enhances the efficacy of the systems and methods shown inFIGS. 7-19, and described in the portion of the specificationcorresponding thereto.

FIG. 22 shows an illustrative flow diagram according to certainconventional embodiments. Step 2202 shows deploying apparatus forrunning systems and methods on a mobile platform. Step 2204 shows asystem failure. The system failure in step 2204 shows that the mobileplatform failed because the mobile platform landed on a databaseconnection page. Step 2204 states that the database connection pagefailed because the database connection page is unreliable as a landingsite for mobile deployment at least in part because of relativelysmaller bandwidth capabilities and the condensed screen associated withtypical mobile devices.

FIG. 23 shows an illustrative flow diagram according to certainembodiments. Step 2302 shows receiving a request for deployment of thesystem on a mobile platform. Step 2304 shows determining which landingsite is independent of a pre-determined database connection, such as anOracle database connection. Step 2306 shows, following determination ofa predetermined-database independent landing site, deploying the mobileplatform.

Thus, methods and apparatus for providing data warehousing with respectto an interactive hierarchical entitlement map are provided. Personsskilled in the art will appreciate that the present invention can bepracticed by other than the described embodiments, which are presentedfor purposes of illustration rather than of limitation, and that thepresent invention is limited only by the claims that follow.

What is claimed is:
 1. A method for bifurcating location of a databased,said bifurcating for enabling presentation and manipulation ofhierarchal client entitlement information in a graphical user interface(“GUI”), the method comprising: querying a list of entitlements for aclient, said list comprising a list of signatories with entitlementauthorization; copying information corresponding to the list ofentitlements from a System of Record, said System of Record being remotefrom said GUI, to a cache memory that is local to the GUI; receivingentitlement authorization for a signatory; adding the signatory to thelist; linking the signatory to one or more signature documentsassociated with the signatory's authorization; receiving a modificationof the client information; transmitting, only if the modification isinput by the signatory, the modification independent of any human inputto the System of Record; and transforming, when received by the Systemof Record, the modified client information into updated clientinformation reflecting the modification.
 2. The method of claim 1,wherein the information corresponding to the list of entitlementscomprises a magnitude that is at least an order of magnitude less thanthe information stored in the System of Record.
 3. The method of claim 1wherein the signatories identified on the list of signatories areauthorized to modify client documents.
 4. The method of claim 1 whereinthe GUI comprises at least three rows of entitlement authorizationlevels, each of the rows of entitlement authorization levelscorresponding to a different level of entitlement authorization, each ofthe rows of the entitlement authorization corresponding to a differentsignatory.
 5. The method of claim 4, wherein the GUI is configured todisplay at least one vertical connection between each signatory in afirst row and at least one signatory in a second row.
 6. The method ofclaim 1 wherein the modification is transmitted independent of humanintervention.
 7. A method for enabling signatory maintenance, saidenabling comprising displaying a graphical user interface (“GUI”), themethod comprising: copying information corresponding to the list ofentitlements from a System of Record, said System of Record being remotefrom THE GUI, to a cache memory local to a device associated with theGUI; displaying on the GUI a list of signatories with at least oneentitlement authorization; receiving a modification of the at least oneentitlement authorization; extracting, from one or more clientdocuments, a signature of a signatory with entitlement authorization;and receiving a user input signal, said user input signal correspondingto a user input device hovering over the signatory; displaying, on ahierarchal display, in response to the hovering: a copy of the signatureof the signatory; a hierarchal list of signatories with currententitlement authorization; and/or a listing of documents signed by eachof the signatories.
 8. The method of claim 7 further comprisingreceiving a change in entitlement for a signatory.
 9. The method ofclaim 8, wherein, in response to the change in entitlement for thesignatory, the method further comprises removing the signatory as anauthorized signor.
 10. The method of claim 8, wherein the listingcomprises a selectable display of documents signed by the signatory. 11.The method of claim 7 wherein the GUI comprises at least three rows ofentitlement authorization levels, each of the rows of entitlementauthorization levels corresponding to a different level of entitlementauthorization, each of the rows of the entitlement authorizationcorresponding to a different signatory.
 12. The method of claim 11,wherein the GUI comprises at least three rows of entitlementauthorization levels, each of the rows of entitlement authorizationlevels corresponding to a different level of entitlement authorization,and wherein the GUI is configured to display at least one verticalconnection between each signatory in a first row and at least onesignatory in a second row.
 13. An apparatus for providing a hierarchalclient entitlement map, the apparatus comprising: a processor configuredto query a list of entitlements for a client; a first System of Recorddatabase, said System of Record being remote from said GUI; a graphicaluser interface (“GUI”) configured to display the list of entitlementsfor the client, wherein the processor is configured to copy informationcorresponding to the list of entitlements from the System of Record, toa cache memory that is local to the GUI; a receiver configured toreceive: from the client, an entitlement authorization level for asignatory; a request to add the signatory to the list; and amodification to the client information; a transmitter configured totransmit, only if the modification is input by the signatory, themodification, independent of any human input, to a System of Record; andthe processor further configured to: link the signatory to one or moresignature documents associated with the signatory's authorization; andtransform, when received by the System of Record, the modified clientinformation into updated client information reflecting the modification.14. The apparatus of claim 13, wherein the signatory is a firstsignatory, the receiver is further configured to: receive, for the firstsignatory, a first entitlement level; and receive, for a secondsignatory, a second entitlement level.
 15. The apparatus of claim 13,wherein the signatories identified on the list of signatories areauthorized to modify client documents.
 16. The method of claim 13,wherein the signatories identified on the list of signatories areauthorized to submit changes to client documents.
 17. The apparatus ofclaim 13, wherein the modification is transmitted using Straight ThroughProcessing.
 18. The apparatus of claim 13, wherein the modification istransmitted without human intervention.
 19. The apparatus of claim 13,wherein the transmitter is further configured to transmit clientinformation in paragraph form.
 20. The method of claim 13, wherein eachof the rows of the entitlement authorization correspond to a differentsignatory.
 21. The method of claim 13, wherein the GUI comprises atleast three rows of entitlement authorization levels, each of the rowsof entitlement authorization levels corresponding to a different levelof entitlement authorization, and the GUI is configured to display atleast one vertical connection between each signatory in a first row andat least one signatory in a second row.